Thread Dump provided.
Submitted | ezust - 2011-12-03 - 17:34:57z | Assigned | nobody |
---|---|---|---|
Priority | 5 | Category | None |
Status | Open | Group | None |
Resolution | None | Visibility | No |
2011-12-04 - 08:46:03z shlomy |
Please try the fix here: http://community.jedit.org/?q=node/view/5011 and let me know if the issue is fixed. For technical reasons I could not update the git repository in SF. It's a new version of MyDoggy that is supposed to fix this deadlock. |
---|---|
2011-12-04 - 16:44:52z ezust |
Downloaded jar from community site. Was able to reproduce deadlock still. Got another thread dump and activity log for you. |
2011-12-04 - 16:45:23z ezust |
oops. sorry, ignore previous comment. I didn't replace the mydoggy jars. |
2011-12-04 - 16:48:53z ezust |
Ok, after replacing all the mydoggy jars, I still can reproduce easily. I just switch between 2 projects that have a few open .java files, and I am using java sidekick too. activity log and 3rd thread dump attached. |
2012-01-28 - 20:07:27z ezust |
Seems to be fixed in ProjectViewer 3.4.1. No longer can reproduce with Mydoggy (git
trunk) version 0.3 |
2012-01-29 - 21:31:55z ezust |
Reopening ticket. Attaching a more recent (deadlock4.txt) thread dump. jEdit 5.0pre1, MyDoggy 0.3, ProjectViewer 3.4.1 |
2012-01-30 - 07:05:25z jarekczek |
Seems to me that Thread-4 is doing things that only EDT is allowed to do. |
2011-12-03 - 17:34:58z ezust |
deadlock-dump.txt |
---|---|
2011-12-04 - 16:44:24z ezust |
activity.log activity log |
2011-12-04 - 16:48:09z ezust |
deadlock-dump3.txt deadlock3 after replacing mydoggy jars |
2012-01-29 - 21:32:16z ezust |
mydoggy-deadlock4.txt |